Bypassing enhanced services

ABSTRACT

A communication environment includes of one or more subscriber terminals capable of initiating emergency voice calls over a telephony network. The subscriber terminal further send messages over either a data network or a telephony signaling network to a communication management system. The communication management system receives messages from a subscriber terminal, either via a data network or a telephony signaling network. It also consists of one or more telephony switching nodes capable of querying the emergency context node for a called party emergency context. It also consists of one or more servers that provide advanced call control services.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/554,750, entitled PROVIDING AND MANAGING BYPASS OF ENHANCED SERVICES,filed Sep. 4, 2009, which claims the benefit of U.S. Provisional PatentApplication No. 61/094,835, entitled SUSPENDING MEDIATED SERVICES, andfiled Sep. 5, 2008, the entireties of which are incorporated herein byreference.

BACKGROUND

In a fixed telephone network or mobile network, emergency calls aregiven a higher priority than normal calls to ensure the greatestpossibility that they are completed successfully. In the event that anemergency call completes to a public safety answering point (“PSAP”)center and then subsequently is disconnected prematurely, it is theobligation of the PSAP center to call back to the originator of theemergency call.

A potential conflict exists between this requirement and advancedtelephony services provided by fixed wire-line and mobile wirelessoperators that perform any form of mediation on incoming calls (e.g.caller screening, selective call blocking, etc.). For example, a prepaidservice that bars call completion to subscribers with a zero balance intheir account may inadvertently block a PSAP center call to a subscriberwho initiated an emergency call that was dropped.

The issue that arises is that a mobile or fixed line carrier can easilyrecognize an initiated emergency call by the dialed digits, “911” inNorth America, “112” in Europe, yet no easy or reliable method isavailable to identify the PSAP center numbers, therefore services thatmediate incoming calls may inadvertently block PSAP center call backs.To avoid conflicts with PSAP call back, incoming calls are not screened.However, failure to screen incoming call limits the effectiveness of anypotential call screening service.

In another approach, a processing server at an advanced screeningservice maintains a number list of all PSAP centers. All calls subjectto possible blocking are screened according to the list. If the incomingcall number is recognized as a PSAP center, the call is completedimmediately without applying any further call screening services.However, lists of appropriate PSAP numbers are difficult to maintain.PSAP centers with multiple telephone lines change numbers on a regularbasis. In smaller rural regions, the emergency calls are very oftenrouted to a local sheriff using a cell phone; this assignment can changeon a daily basis based on shift rotations in the sheriff's office. Theseremote office lines, agency issued mobile devices or personal devicesmay not be recorded in the PSAP call center database.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of thisinvention will become more readily appreciated as the same become betterunderstood by reference to the following detailed description, whentaken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram illustrative of one embodiment of acommunication management environment including a communicationmanagement system and a number of mobile communication devices;

FIG. 2 is a block diagram illustrative of aspects of the communicationmanagement system of FIG. 1 in an embodiment of the communicationmanagement environment;

FIG. 3 is a block diagram illustrative of aspects of the mobilecommunication device of FIG. 1 in an embodiment of the communicationmanagement environment;

FIGS. 4A-4C are block diagrams of the communication management system ofFIG. 1 illustrating the transmission of mobile communication devicecontext information by a mobile device and the processing by thecommunication management system of communication channel initiationrequests submitted by a third party communication device;

FIGS. 5A-5C are block diagrams of the communication management system ofFIG. 1 illustrating the transmission of mobile communication devicecontext information by a mobile device and the processing by thecommunication management system of communication channel initiationrequests submitted by the mobile communication device;

FIG. 6 is a block diagram of the communication management system of FIG.1 illustrating the transmission of updated mobile communication devicecontext information by a mobile communication device and the processingof an ongoing communication channel by the communication managementsystem;

FIGS. 7A-7E are flow diagrams illustrative of travel state contextassessment algorithm implemented by a mobile communication device inproviding mobile communication device context information to acommunication management system;

FIG. 8 is a flow diagram illustrative of a geospatial context assessmentalgorithm implemented by a mobile communication device in providingmobile communication context information to a communication managementsystem;

FIG. 9 is a flow diagram illustrative of a communication managementroutine implemented by a communication management system for managingcommunications according to mobile communication device contextinformation;

FIG. 10 is a block diagram illustrative of a screen display of a userinterface for obtaining mobile communication device profile informationfor managing mobile communication device availability based on mobilecommunication device context information;

FIG. 11 is a block diagram illustrative of a screen display of a userinterface for obtaining mobile communication device profile informationfor managing mobile communication device availability based on mobilecommunication device context information;

FIGS. 12A-12C are block diagrams of the communication management systemof FIG. 1 illustrating the bypassing of mitigation techniques by thecommunication management system for communications between a mobilecommunication device and PSAP center;

FIG. 13 is a flow diagram illustrative of a call mitigation bypassingprocessing routine implemented by a communication management component;

FIG. 14 is a flow diagram illustrative of a call mitigation bypassinitiation routine implemented by a mobile device; and

FIG. 15 is a flow diagram illustrative of a call mitigation bypassprocessing routine implemented by a network node.

DETAILED DESCRIPTION

The present disclosure consists of one or more mobile devices capable ofinitiating emergency voice calls over a telephony network. The mobiledevices further send messages over either a data network or a telephonysignaling network to a communication management component. The emergencycontext server receives messages from a subscriber terminal, either viaa data network or a telephony signaling network. It also consists of oneor more telephony switching nodes capable of querying the communicationmanagement component for a called party emergency context. It alsoconsists of one or more servers that provide advanced call controlservices.

Although aspects of the system will be described to the drawings, flowdiagrams, screen interfaces, and specific examples, one skilled in therelevant art will appreciate that the disclosed embodiments areillustrative in nature. Accordingly, the disclosed embodiments shouldnot be construed as limiting.

System Overview

With reference now to FIG. 1, a block diagram illustrative of acommunication management environment 100 for managing mobilecommunication device communications will be described. As illustrated inFIG. 1, the communication management environment 100 includes acommunication management system 102 for processing requests forestablishing a communication channel between a supported mobile deviceand a third party communication device. The communication managementsystem 102 maintains mobile communication device profiles that areprovisioned to establish the availability for the mobile communicationdevice to establish a communication channel as a function of mobilecommunication device context information. The communication deviceprofiles may also be provisioned as a function of identificationinformation of an applicable third party. As will also be described ingreater detail below, the communication management system 102 determinesthe availability of the mobile device to establish a communicationchannel asynchronously to any request to establish a communicationchannel.

To manage requested communications or previously establishedcommunication channels, the communication management system 102communicates with corresponding subsystems responsible for establishingthe wireless communication channel, such as mobile switching center 108,and utilizes the predetermined availability information and appropriateidentification information to allow/reject communications. Thecommunication management system 102 can communicate with the mobileswitching center 108 via a direct communication connection, a securecommunication channel via a communication network, such as communicationnetwork 114, or via a public communication network.

Additionally, the communication management system 102 providescommunication channel mitigation options in the event that the mobilecommunication device is unavailable, which can include interfacing witha communication mitigation components 103, such as a voice mail systemor an interactive voice response system. Still further, thecommunication management system 102 facilitates the generation ofvarious graphical user interfaces for provisioning and/or managingmobile communication device profiles via computing devices 116.Illustrative components of the mobile communication management systemwill be described in greater detail with regard to FIG. 2.

With continued reference to FIG. 1, the communication managementenvironment 100 can include a number of mobile communication devices104. The mobile communication devices 104 can correspond to wide varietyof devices or components that are capable of initiating, receiving orfacilitating communications over a communication network including, butnot limited to, personal computing devices, hand-held computing devices,integrated components for inclusion in computing devices, homeelectronics, appliances, vehicles, and/or machinery, mobile telephones,modems, personal digital assistants, laptop computers, gaming devices,and the like. In an illustrative embodiment, the mobile communicationdevices 104 include a wide variety of software and hardware componentsfor establishing communications over one or more communication networks,including wireless or wired mobile communication networks 106. Themobile communication devices 104 can be associated with one or moreusers for managing communication channel requests and existingcommunication channels according mobile communication device contexts.Illustrative components of a mobile communication device will bedescribed in greater detail with regard to FIG. 3.

With continuing reference to FIG. 1, an illustrative communicationmanagement environment 100 can include a number of additionalcomponents, systems and/or subsystems for facilitating communicationswith the mobile communication devices 104 and/or the communicationmanagement system 102. The additional components can include one or moremobile switching centers 108 for establishing communications with themobile communication devices 104 via the mobile communication network106, such as a cellular radio access network, a wireless network basedon the family of IEEE 802.11 technical standards (“WIFI™”), a wirelessnetwork based on IEEE 802.16 standards (“WIMAX™”), and other wirelessnetworks. The operation of mobile communication networks, such as mobilecommunication network 106 are well known and will not be described ingreater detail.

As illustrated in FIG. 1, the mobile switch center 108 includesinterfaces for establishing various communications with via thecommunication network 116, such as the Internet, intranets, privatenetworks, and point-to-point networks. In one example, the mobile switchcenter 108 can include interfaces for establishing communicationchannels with various communication devices 112, such as landlinetelephones, via a public switched telephone network (PSTN) 110. As willbe described in greater detailed below, the mobile switch center 108 canfacilitate communication channels between the mobile devices 104, thecommunication management system 102 and a PSAP center 114.

The mobile switch center 108 can also include interfaces forestablishing communication channels with various communicationnetwork-based communication devices 112, such as a VoIP communicationdevice. Still further, the mobile switch center 108 can includeinterfaces for establishing communication channels with a mobile-basedcommunication device 112, such as another mobile communication device.For example, the communication devices 112 can correspond to athird-party mobile communication that establishes an audio communicationchannel with a mobile communication device 104. Accordingly, althoughcommunication network 116 is illustrated as a single communicationnetwork, one skilled in the relevant art will appreciate that thecommunication network can be made up of any number of public or privatecommunication networks and/or network connections.

The various communication devices 112 can include the hardware andsoftware components that facilitate the various modes of operation andcommunication, such as via wired and wireless communication networks.Additionally, the computing devices 118 can include various hardware andsoftware components, such as a browser software application, thatfacilitate the generation of the graphical user interfaces forprovisioning and managing mobile communication device profiles as willbe described below.

One skilled in the relevant art will appreciate that the components andconfigurations provided in FIG. 1 are illustrative in nature.Accordingly, additional or alternative components and/or configurations,especially regarding the additional components, systems, and subsystemsfor facilitating communications may be utilized.

With reference now to FIG. 2, illustrative components for thecommunication management system 102 will be described. Although theoperation of the various functions associated with the communicationmanagement system 102 will be described with regard to belowsubcomponents, one skilled in the relevant art will appreciate that thesubcomponents are illustrative in nature. Accordingly, a communicationmanagement system 102 may include additional components or alternativecomponents to facilitate one or more functions. Additionally, althoughthe various subcomponents are illustrated as integrated into acommunication management system 102, one or more of the components maybe implemented in a distributed manner over a communication networkand/or be implemented as a network service, e.g., a Web service.

As illustrated in FIG. 2, the communication management system 102includes a mobile device communication component 202 for establishingcommunications with a mobile communication device 104. In anillustrative embodiment, the mobile device communication component 202corresponds to a component for facilitating the bi-lateral transfer ofdata, such as mobile device context information, context assessmentalgorithms, etc., between the mobile communication device 104 and thecommunication management system 102. The mobile device communicationcomponent 202 can include software and hardware components necessary toestablish one or more communication channels corresponding to variouscommunication protocols such as BLUETOOTH™, the family of IEEE 802.11technical standards (“WIFI™”), the IEEE 802.16 standards (e.g.,“WIMAX™”), short message service (“SMS”), voice over IP (“VoIP”) as wellas various generation cellular air interface protocols (including, butnot limited to, air interface protocols based on CDMA, TDMA, GSM, WCDMA,CDMA2000, TD-SCDMA, WTDMA, LTE, OFDMA and similar technologies).

The communication management system 102 can also include a communicationprocessing component 204 for determining the availability of a mobilecommunication device 104 for communication channels based on processingmobile communication device context information according to a mobilecommunication device profile. The communication processing component 204can execute various processes or algorithms for processing transmittedmobile communication device context information to determine mobilecommunication device availability. Additionally, the communicationprocessing component 204 can also manage the various context assessmentprocesses or algorithms and updates to existing previously storedcontext assessment processes and algorithms that are transmitted andexecuted by the mobile communication devices 104. Still further, thecommunication processing component 204 processes requests forcommunications between the mobile communication device 104 and thirdparties based on the predetermined availability information andidentification information (e.g., the caller ID of a specific thirdparty caller). Still further, the communication processing component 204can further manage mobile device 104 context state to determine whethermitigation services should be applied to a communication request basedon exception rules. such as an emergency bypass context state.

With continued reference to FIG. 2, the communication management system102 can include a communication mitigation component 206 for processingalternative communication options if a requested communication channelis unavailable or if an existing communication is to be terminated dueto a change in mobile communication device context. As previouslydiscussed, the communication mitigation component 206 can interface withexisting communication components, or subsystems, such as mitigationcomponents 103 for providing user voicemail functionality or accessingexisting voicemail services hosted by the mobile switching center 108.Additionally, the communication mitigation component 206 can provideadditional data and/or instructions for establishing alternativecommunication channels between the mobile device and a third partycommunication device 112, such as providing interactive voice responsefunctionality, as will be explained in greater detail below. Stillfurther, the communication management system 102 can include a mobileservice provider communication component 208 for processing requests forestablishing communications, which includes indicating to a mobileswitching center 108 whether to allow a requested communication channelto be established and/or indicating whether to terminate an existingcommunication channel. Although the communication management system 102is illustrated a functional to implement multiple functions, one skilledin the relevant art will appreciate that the communication managementsystem 102 may be arranged as a collection of separate componentdirected to carry out one or more functions associated with thecommunication management system. For example, a bypass state server maybe configured for purposes of determining whether call mitigationtechniques should be bypassed.

The communication management system 102 can further include a mobilecommunication device profile data store 210 for maintaining mobilecommunication device profiles. The mobile communication device profiledata store 210 may be one or more databases configured to provide thecommunication processing component 204 required data to determine mobilecommunication device availability according to mobile communicationdevice context. As will be described in greater detail below, the mobilecommunication device profile data defines the availability of the mobilecommunication device 104 as a function of a current mobile communicationdevice context. A mobile communication device profile can be definedsuch that the determined mobile communication device applicability willbe applicable to all third party users, groups of users or specificusers. For example, profiles can be associated with a telephone numbersuch that the communication manage system 102 can select an appropriateprofile (and its predetermined availability) based on identificationinformation associated with a communication request, such as calleridentity information. Accordingly, the mobile communication deviceprofile information in the communication device profile data store 210can be stored in a manner that facilitates that faster retrievalaccording to identification information, as will be described in greaterdetail below. Still further, in another embodiment, the mobilecommunication device context data store 212 can be utilized to mitigatethe initiation of mitigation services in the event a mobile device 104is in specific context states, such as an emergency context state.

With continued reference to FIG. 2, the communication management system102 can also include a mobile communication device context data store212 for maintaining mobile communication device context informationpreviously transmitted by the mobile communication devices 104 and/orfor maintaining the mobile communication device context assessmentalgorithms utilized by the mobile communication devices to processinputs into mobile communication device context. In one embodiment, themobile communication device context information may be accessible, orotherwise published, to other computing devices, network based services,or users via the communication network 114.

With reference now to FIG. 3, illustrative components for the mobilecommunication device 104 will be described. Although the operation ofthe various functions associated with the mobile device 104 will bedescribed with regard to below components, one skilled in the relevantart will appreciate that the components are illustrative in nature.Accordingly, a mobile device 104 may include additional components oralternative components to facilitate one or more functions.Additionally, although the various subcomponents are illustrated asintegrated into a mobile device 104, one or more of the components maybe implemented in a distributed matter over a communication networkand/or be implemented as a network service, e.g., a Web service.

As illustrated in FIG. 3, the mobile device 104 includes a communicationmanagement system communication component 302 for facilitatingcommunications with the communication management system 102. Asdescribed above with regard to the mobile device communication component202 (FIG. 2), the communication management system communicationcomponent 302 facilitates the bi-lateral transfer of data between themobile communication device 104 and the communication management system102. One skilled in the relevant art will appreciate that thecommunication management system communication component 302 can includesoftware and hardware components necessary to establish one or morecommunication channels corresponding to various communication protocolsfor establishing the bi-lateral communication channels. Moreover,although the communication management system communication component 302is illustrated as a separate component, the functionality of thecomponent may be integrated, or otherwise combined, with one or morehardware or software components utilized by the mobile communicationdevice 104 to make communication channels (e.g., cellular communicationchannels or SMS communication channels as part of the designed functionof the mobile device).

As will be described in greater detail below, the communicationmanagement system communication component 302 transmits current mobiledevice context information in accordance with the context assessmentalgorithms on the mobile device 104. Once a current mobile communicationdevice context is established, the communication management system 302can limit additional transmission of context information upon detectionof a change in mobile communication context information. Additionally,in an alternative embodiment, the communication management systemcommunication component 302 may also transmit, or otherwise publish,mobile communication device context information to additionalrecipients, such as communication network resources such as Web sites ornetwork services, and/or to other peer destinations.

The mobile communication device 104 can also include a mobilecommunication device context information component 304 for processing aset of inputs corresponding to a mobile device environment to determinemobile device context information. Illustrative context assessmentalgorithms or processes for determining mobile device contextinformation will be described in greater detail below. The mobilecommunication device contexts can identify or describe aspects of themobile communication device 104, aspects of the mobile communicationdevice environment, and/or aspects of the user associated with themobile communication device. For example, the mobile communicationdevice context corresponds to a determination of various states ofmovement/travel, such as in a non-transitory state, an in-transit state(including city/urban travel transit, highway transit, and in-flighttransit states), a journey onset state, and a journey termination state.In another example, the mobile communication device context correspondsto a determination of whether a mobile communication device's presentlocation is within a geospatial boundary, also referred to asgeofencing, (including within the geospatial boundary, on a border ofthe geospatial boundary, or outside the geospatial boundary). Oneskilled in the relevant art will appreciate that the identified mobiledevice contexts are not exhaustive and that any number of additionalmobile device contexts, or variations of the identified mobilecommunication device contexts, may also be defined for the mobilecommunication device 104.

With continued reference to FIG. 3, the mobile communication device 104can also include a mobile communication device environment interface 306for obtaining inputs corresponding to a mobile communication deviceenvironment. In an illustrative embodiment, the set of inputs caninclude information from one or more sensors such as a global positionsensor (GPS) component or other location identification components,accelerometers, altimeters, compasses, gyroscopes, microphones, scalesor other weight detection mechanisms, range finders, proximity sensors,gas or radiation detectors, electric current or electric inductiondetection, digital image sensors, thermometers and the like.Additionally, the set of inputs can correspond to information obtainedfrom communication network based resource such as calendaringinformation, identity or contact information and the like.

In one embodiment, the set of inputs include information from sensors orinformation gathering components that are integrated or attached to themobile computing device 104. In another embodiment, the set of inputsinclude information from external sensors or information gathercomponents that provide the information via a communication channel,such as a hardwired connection or wireless connection (e.g.,BLUETOOTH™). Still further, in another embodiment, the set of inputsinclude information related to sensors or processed information fromanother device or article of manufacture associated with the mobilecommunication device. For example, the set of inputs can includeinformation from a vehicle computer indicating information about theoperation/condition of the vehicle and/or environmental information.Additional information from seat sensors may be able to inform that theremote end user is indeed a passenger and not a driver, and further,that seat belts are engaged. Still further, in another embodiment, theset of inputs include information from sensors that can be repurposed,such as through additional processing, to determine mobile communicationdevice context information. For example, image data from a camera sensoror signal data from a transceiver chipset may be utilized as inputs to acontext assessment algorithm to determine mobile communication devicecontext. The above provided identification of the specific types ofsensors is not exhaustive. Accordingly, additional or alternativesensors may be utilized to provide information for determining mobilecommunication device context information.

One skilled in the relevant art will appreciate that the set of inputsmay be selected to correspond specifically to the particular algorithmsutilized to calculate mobile communication device context. In oneexample, microphonic sensors may used for detecting high noise levelsfrom the embedded device microphone and using this context to permitonly high importance work related calls and data session requests thatpertain to the current work function. Furthermore, the mobile devicecontext information can be utilized to inform the calling party that thecallee is in a high noise environment and that a text message may be amore appropriate. In another example, the sensor information cancorresponds to a determination whether a BLUETOOTH™ headset oralternative hands free device is active in accordance with a corporatepolicy and local jurisdiction law. In still a further example, radiationdetector sensor information could be utilized to detect increases inradioactive levels. The context could be utilized to immediatelyinstruct the call and data session management control to connect themobile end users with an emergency response team and autonomously reportexisting location and radiation levels just in case the mobile end useris incapacitated by some external cause.

In still a further example, gas or substance detector sensors could beutilized to detect an increase in gas or substance levels. The contextcould be utilized to immediately instruct the call and data sessionmanagement control to connect the mobile end users with an emergencyresponse team and autonomously report existing location and gas andsubstance levels just in case the mobile end user is incapacitated bysome external cause. In yet another example, utilization near fieldinductive techniques sensors could be utilized to detect the process ofcharging via near field inductive components. The context could be usedsuch that a call and data session management entity should perhaps bereroute calls and data session requests to different devices.

In still another example, proximity sensor information could be used todetermine a context that the user is currently interacting in a specificmanner with the mobile end device may enable specific call and datasession management decisions to be critically enabled. In a furtherexample, image data from a mobile device camera may be utilized viasignal context assessment algorithms to determine the user'senvironment. In another example, user configurable keys/control sensordata can be utilized to customize mobile device context information,such as using soft keys, to register specific contexts provided by themobile communication device user (e.g., “watch me,” “help,” etc.).

The mobile communication device 104 can further include a mobilecommunication device data store 308 for storing input information fromthe mobile communication device environment interface 306, contextinformation generated by the mobile communication device processingcomponent 304 and/or the various context assessment algorithms orprocesses used by the mobile communication device processing componentto generate the mobile communication device context information.

Communication Mitigation

As described in FIG. 1, the communication management environment caninclude a communication mitigation component 103. FIGS. 4-18 describeillustrative architectures, interactions, methodologies, and interfacesfor facilitating communication mitigation in accordance with an aspectof the present disclosure. A more detailed example of communicationmitigation is described in U.S. patent application Ser. No. 12/040,832,entitled MANAGEMENT OF MOBILE DEVICE COMMUNICATION SESSIONS TO REDUCEUSER DISTRACTION, and filed Feb. 29, 2008, the entirety of which isincorporated by reference herein. However, one skilled in the relevantart will appreciate that alternative, modified or additionalarchitectures, interactions, methodologies, and interfaces forfacilitating communication mitigation are also included within the scopeof the present disclosure. Accordingly, the disclosed and referencedexamples are illustrative in nature and should not be construed aslimiting.

With reference now to FIG. 4-6, the interaction between variouscomponents of the communication management environment 100 of FIG. 1will be illustrated. For purposes of the example, however, theillustration has been simplified such that many of the systems,subsystems, and components utilized to facilitate communications are notshown. One skilled in the relevant art will appreciate that suchcomponents or subcomponents can be utilized and that additionalinteractions would accordingly occur without departing from the spiritand scope of the present invention.

With reference now to FIGS. 4A-4C, one embodiment related to theprocessing of a request from a third party communication device 112 toestablish a communication channel, such as an audio call, will bedescribed. For purposes of the illustrative example, a particular mobilecomputing device 104 has registered with a communication managementservice that provides the communication management system 102.Additionally, a user of the mobile device 104 has provisioned a mobilecommunication device profile that identifies the availability of themobile communication device as a function of mobile communication devicecontexts and third party identification information. Alternatively, someportion the mobile communication device profile may be pre-provisionedfor the user and/or automatically set by an administrator, such as aservice provider.

As illustrated in FIG. 4A, during the operation of the mobilecommunication device 104, or during an initialization of the mobilecommunication device, the mobile communication device interfacecomponent 306 obtains a set of inputs corresponding to the mobilecommunication device environment. The set of inputs are processed by themobile communication device context processing component 304 to generatemobile communication device context information. The communicationmanagement system communication component 302 than transmits the mobilecommunication device context information to the communication managementsystem 102 as appropriate. Specifically, to reduce power consumptionand/or bandwidth consumption, the communication management systemcommunication component 302 may limit the transmission of mobilecommunication device context information for the initialization of amobile communication device context, a detection of a change in mobilecommunication device context and/or for the re-establishment of a mobilecommunication device context.

Upon receipt of the context information, the mobile device communicationcomponent 202 transmits the context information to the communicationprocessing component 204 for processing. The communication processingcomponent 204 obtains a corresponding, or applicable, mobilecommunication device profiles from the mobile communication deviceprofile data store 210. The communication processing component 204 mayutilize one or more mobile communication device profiles to determinemobile communication device availability from the context information.Alternatively, a single mobile communication device profile may defineavailability for multiple mobile communication device contexts. Thecommunication processing component 204 then determines the availabilityof the mobile communication device to establish a communication channel(either receipt of a request or the initiation of a request) based onthe processing.

Thereafter, in the illustrative example of FIG. 4A, a communicationdevice 112, such as a third party communication device 112 initiates arequest to establish a communication channel with the mobile device 104.The request is received by the mobile switching center 108 and is heldpending an approval or rejection by the communication management system102. The applicable mobile switching center 108 then transmits therequest to the mobile service provider communication component 208 torequest a determination whether the requested communication channelshould be established. The request can include additional informationutilized by the communication management component 102 to select anappropriate profile, including caller identification information and thelike.

With reference now to FIG. 4B, upon receipt of the request ornotification from the mobile switching center 108, the communicationprocessing component utilizes the predetermined availability of themobile communication device 104 to authorize or reject the establishmentof the requested communication channel. If the request to initiate thecommunication channel is authorized, the authorization is transmitted tothe mobile switching center 108, which processes the request forinitiation of the communication channel in an appropriate manner.Accordingly, the requested communication channel is completed. As willbe described in greater detail below with regard to FIG. 9, thecommunication management system 102 may continue to monitor theestablished communication channel for a change in mobile communicationdevice context and will manage the communication channel as defined inthe applicable mobile communication device profile.

With reference now to FIG. 4C, alternatively, if the request forinitiation of the communication channel is rejected based on apredetermined unavailability of the mobile communication device 104, thecommunication management component 102 transmits a rejectionauthorization communication to the mobile switching center 108 toprevent the initiation of the communication channel. Additionally, thecommunication mitigation component 206 can provide appropriatecommunication mitigation, such as notifications to the users of themobile communication device 104 and the communication device 112.Additionally, the communication management component 102 can obtain aselection of a communication channel alternative defined in the mobilecommunication device profile, such as voicemail systems or interactivevoice response systems, as will be described in greater detail below.

With reference now to FIGS. 5A-5C, one embodiment processing of arequest from a user at a mobile communication device 104 to establish acommunication channel, such as an audio call, with a third partycommunication device 112 will be described. As described above withregard to FIGS. 4A and 4B, for the illustrative example, it is assumedthat a particular mobile computing device 104 has registered with acommunication management service that provides the communicationmanagement system 102 and provisioned a mobile communication deviceprofile that identifies the availability of the mobile communicationdevice for particular mobile communication device contexts.

As illustrated in FIG. 5A, during the operation of the mobilecommunication device 104, or during an initialization of the mobilecommunication device, the mobile communication device interfacecomponent 306 obtains a set of inputs corresponding to the mobilecommunication device environment. The set of inputs are processed by themobile communication device context processing component 304 to generatemobile communication device context information. The communicationmanagement system communication component 302 then transmits the mobilecommunication device context information to the communication managementsystem 102 as appropriate. Specifically, to reduce power consumptionand/or bandwidth consumption, the communication management systemcommunication component 302 may limit the transmission of mobilecommunication device context information for the initialization of amobile communication device context, a detection of a change in mobilecommunication device context and/or for the re-establishment of a mobilecommunication device context.

Upon receipt of the context information, the mobile device communicationcomponent 202 transmits the context information to the communicationprocessing component 204 for processing. The communication processingcomponent 204 obtains one or more corresponding, or applicable, mobilecommunication device profiles from the mobile communication deviceprofile data store 210. The communication processing component 204 thendetermines the availability of the mobile communication device toestablish a communication channel (either receipt of a request or theinitiation of a request) based on the processing.

Thereafter, in the illustrative example of FIG. 5A, the mobile device104 initiates a request to establish a communication channel with acommunication device 112, such as a third party communication device112. The request is received by the mobile switching center 108 and isheld pending an approval or rejection by the communication managementsystem 102. The applicable mobile switching center 108 then transmitsthe request to the mobile service provider communication component 208,along with additional information, such as the identificationinformation (e.g., telephone number) of the third party communicationdevice 112.

With reference now to FIG. 5B, upon receipt of the request ornotification from the mobile switching center 108, the communicationprocessing component obtains applicable communication profiles using theidentification information or other information and utilizes thepredetermined availability of the mobile communication device 104 toauthorize or reject the establishment of the communication channel. Ifthe request to initiate the communication channel is authorized, theauthorization is transmitted to the mobile switching center 108, whichprocesses the request for initiation of the communication channel in atypical manner. Accordingly, the requested communication channel iscompleted. As will be described in greater detail below with regard toFIG. 9, the communication management system 102 may continue to monitorthe established communication channel for a change in mobilecommunication device context.

With reference now to FIG. 5C, alternatively, if the request forinitiation of the communication channel is rejected based on adetermined unavailability of the mobile communication device 104, thecommunication management component 102 transmits a rejectionauthorization communication to the mobile switching center 108 toprevent the initiation of the communication channel. Additionally, thecommunication mitigation component 206 can provide appropriatenotifications to the users of the mobile communication device 104 andthe communication device 112. Additionally, the communication managementcomponent 102 can obtain a selection of a communication channelalternative as will be described in greater detail below.

With reference now to FIG. 6, in the event that a communication channelhas been established between a mobile communication device 104 and acommunication device 112, the communication management system 102continues to determine the availability of the mobile communicationdevice 104 to remain in the established communication channel. Asillustrated in FIG. 6, the mobile communication device 104 continues toreceive sensor information and determine mobile communication devicecontext information. In the event that the mobile communication devicecontext information has changed or is otherwise no longer valid, thecommunication management component 302 of the mobile device mobiletransmits the updated mobile communication device context information tothe communication management system 102. In one embodiment, the mobiledevice communication component 202 may only transmit updated contextinformation in the event that a change in context is determined.Alternatively, the mobile device communication component 202 maytransmit update context information after a predetermined time. Becausethe mobile device 104 has an established communication channel with thecommunication device 112, the communication management systemcommunication component 302 may have to utilize a differentcommunication channel (such as an SMS channel) to transmit the updatedcontext information if the communication channel previously utilized totransmit the context information is being utilized for the establishedcommunication channel.

Upon receipt of the context information, the mobile device communicationcomponent 202 transmits the context information to the communicationprocessing component 204 for processing. The communication processingcomponent 204 obtains one or more corresponding, or applicable, mobilecommunication device profiles from the mobile communication deviceprofile data store 210. The mobile communication device profile may bethe same profile previously utilized to determine the availability ofthe mobile communication device or an additional or alternative mobilecommunication device profiles. As previously described, the selection ofthe appropriate or applicable profile stores can include the utilizationof identification information, such as caller ID information. Thecommunication processing component 204 then determines the availabilityof the mobile communication device to maintain the establishedcommunication channel based on the profiles. If it is determined tomaintain the established communication channel, the communicationmanagement system 102 can transmit an authorization message or remainsilent. Alternatively, if the communication channel should be terminatedbased on a determined unavailability of the mobile communication device104, the mobile service provider communication component can transmitcommunication channel control information that includes a terminationnotification to the mobile switching center 108. Additionally, thecommunication mitigation component 206 can provide appropriatecommunication channel mitigation information, such as notifications tothe users of the mobile communication device 104 and the communicationdevice 112 and provide a selection of a communication channelalternative as will be described in greater detail below.

A. Mobile Device Context Assessment Algorithms

With reference now to FIGS. 7A-7E, an illustrative routine 1200implemented by the mobile communication device context processingcomponent 304 for determining context information of a mobilecommunication device 104 will be described. As described above, themobile communication device context can correspond to a determination ofa specific transit state indicative of a current mobile communicationdevice environment. The availability for a communication channel may bebased on the determined transit state and the appropriate mobilecommunication device profile. With reference to an above mentionedexample, a user can provision a mobile device profile such that callsfrom an identified user are rerouted automatically to a voicemail systemin the event that mobile device (e.g., the user) is in a city/urbantransit state. As will be described, in event that the mobilecommunication device 104 determines it is currently in a city/urbantransit state, the mobile communication device transmits the updatedcontext information to the communication management component 102, whichdetermines the availability/unavailability information based on theupdated context information for all profiles. Thereafter, calls from theidentified users are rerouted automatically without the need to poll themobile communication device 104 until the mobile communication deviceprovides updated context information.

With reference now to FIG. 7A, at block 702, the routine 700 begins withthe initialization of the transit state to non-transit by the mobilecommunication device context processing component 304. In anillustrative embodiment, the non-transit state is a first stateindicative of when the mobile communication device 104 is powered on orbegins tracking transit state. The initialization of the transit stateto nontransit may be transmitted to the communication management system102 or may be assumed as the starting context for the mobilecommunication device 104. At decision block 704, a test is conducted todetermine whether minimum movement criteria have been satisfied based onprocessing the set of inputs. For example, the test can correspond to areview of velocity input(s) and distance traveled input(s) to determinewhether the input values exceed a minimum threshold.

Velocity and distance information can be obtained by the mobilecommunication device through a variety of sensors and/or componentsdesigned to generate or calculate such information. Examples include,but are not limited to, GPS devices/components, accelerometers,navigational equipment, and the like. As previously described, thesensors and/or components may be integrated into the mobilecommunication device 104 or may be separate components (e.g., a carnavigation system) that provide the input information via a wired orwireless connection.

In another example, the velocity and distance information may becalculated by the mobile communication device 104 through by theutilization of recognizable or detectable objects. In accordance withthis example, the mobile communication device 104 receives signalsgenerated by fixed transmitters, such as cellular communications basestations or WIFI™ wireless nodes, which generally include someidentification information specific to the particular transmitter, suchas an SSID for a wireless node. As a mobile communication device 104travels, signals from specific transmitters are detected when the mobilecommunication device is within range of the transmitter and no longerdetected when the mobile communication device is beyond the range of thetransmitter. For known communication ranges of transmitters, such asWIFI™ wireless nodes, velocity and distance traveled information may becalculated based on monitoring time from the detection of a signal froma transmitter to loss of the signal. Additionally, the detection of thesignal from the transmitter would not require registration with thetransmitter and could still be practiced with transmitters that restrictaccess, such as through encrypted transmissions.

If the minimum movement criteria have not been satisfied, it is assumedthat the mobile communication device (considering its environment) isstill in a non-transit state and the routine 700 returns to block 702.The routine 700 may continue to loop through this portion for any amountof time.

Alternatively, if the minimum movement criteria have been satisfied, itis assumed that the mobile communication device 104 (considering itsenvironment) is in motion, and at block 706, the transit state ischanged to a “journey onset state.” Because the transit state haschanged, the mobile communication device 104 may transmit updatedcontext information to the communication management component 102indicative of the change in transit state to a journey onset state. Atblock 708, the mobile communication device context processing component304 enters an observation window for collecting the various inputs overa period of time. The observation window can be configured such that themobile communication device 104 collects a fixed number of sets asdefined by an information collection interval over a time period. Eachtime a set of inputs is collected a counter is decremented and theprocess continues until the targeted number of sets on inputs have beencollected (e.g., the counter is decremented to a value of “0”).Additionally, if the mobile communication device environment interface306 is currently not receiving inputs, or otherwise not acceptinginputs, the mobile communication device 104 may enter a lower powerconsumption mode in which one or more components of the mobilecommunication device 104 become inactive or enter in a low powerconsumption mode of operation. In turn, the mobile communication device104 then powers up, or wakes up, at the next information collectioninterval. The specific information collection interval implemented bythe mobile communication device context processing component 304 may bedependent on the granularity of the sensor information, the amount ofinput information that should be collected for a given transit state,and/or the likelihood of a potential change in transit state. Forexample, a longer collection interval can be set for transit states inwhich variations in the set of inputs is not expected (e.g. a highwaytransit state) to further conserve mobile communication device power.

Upon the expiration of the time window, at decision block 710, a test isconducted to determine whether minimum movement criteria have beensatisfied based on processing the set on inputs. If the minimum movementcriteria have not been satisfied, the mobile communication device 104 isdetermined to be no longer in motion and the routine 700 returns toblock 702 to a “non-transit” travel state (described above). Because thetransit state has changed, the mobile communication device 104 maytransmit updated context information to the communication managementcomponent 102 indicative of the change in transit state back to anon-transit state.

With reference now to FIG. 7B, alternatively, if at decision block 710(FIG. 7A), the minimum movement criteria have been satisfied, at block712, the mobile communication device 104 is determined to be in motionand the transit state is changed to a “city/urban” transit state. In anillustrative embodiment, the city/urban transit state can correspond tothe driving conditions experienced in city or urban areas in which thereare frequent stops and wide changes in velocity. Again, because thetransit state has changed, the mobile communication device 104 maytransmit updated context information to the communication managementcomponent 102 indicative of the change in transit state back to anon-transit state. At block 714, the mobile communication device contextprocessing component 304 enters an observation window that defines a setof intervals for collecting multiple sets of inputs over a period oftime. In a city/urban transmit state, the collection interval forreceiving each set of inputs may be configured to be shorter because ofthe potential for greater variances in the information from set ofinputs.

At decision blocks 716-718, the mobile communication device contextprocessing component 304 processes the collected input data to determinewhether the mobile communication device 104 should remain in its currentcity/urban transit state, whether the mobile communication device hasreached a terminus state, or whether the transit state is moreindicative of another transit state typically indicative of highwaytravel. The collected information can include velocity, bearing, anddistance traveled information. Additionally, the collected informationcan include processed velocity, bearing and distance traveledinformation, referred to as variance information, that indicatevariances and/or rates of variance in the velocity, bearing and distancetraveled over each of the collection intervals in the observed timewindow.

At decision block 716, a test is conducted to determine criteriaindicative of city/urban transit state have been satisfied. The criteriaindicative of city/urban transit state can correspond to considerationof variance thresholds for velocity, distance traveled and bearing thatare indicative of patterns of city/urban travel. For example, velocityvariances for a city/urban transit state may be indicative of acollection of inputs at a time in which a vehicle is stopped (e.g., at astreet light) and another collection when the vehicle is traveling at ahigher velocity. The thresholds may be determined by observed drivingbehavior, set by an administrator or set by a particular user. If thecriteria indicative of city/urban transit state have not been satisfied,the mobile communication device context processing component 304determines that the mobile communication device 104 is not likely in acity/urban driving embodiment and moves to block 726, which will bedescribed in greater detail below. Alternatively, if the criteriaindicative of city/urban transit state have been satisfied, the mobilecommunication device context processing component 304 determines thatthe mobile communication device 104 should either remain in a city/urbantravel state or has reached a terminus. Accordingly, at decision block718, a test is conducted to determine whether minimum movement criteriahave been satisfied based on processing the set on inputs. If theminimum movement criteria have not been satisfied, the mobilecommunication device 104 is determined to be no longer in motion and theroutine 700 proceeds to block 720 (FIG. 7C). Alternatively, if theminimum movement criteria have been satisfied, the routine 700 returnsto block 712. In this instance, however, the mobile communication device104 does not need to transmit context information to the communicationmanagement component 102 because the transit state has not changed.

With reference now to FIG. 7C, at block 720, the transit state of themobile communication device is changed to a “journey terminus” transitstate. In an illustrative embodiment, the journey terminus transit statecan correspond to the completion of the initial travel. As previouslydescribed, because the transit state has changed, the mobilecommunication device 104 may transmit updated context information to thecommunication management component 102 indicative of the change intransit state. At block 722, the mobile communication device contextprocessing component 304 enters an observation window in which acollection interval may be set to a shorter time period because of theexpectation for a higher variance between the sets of inputs at eachcollection interval.

Upon the completion of the observation window, the mobile communicationdevice context processing component 304 will determine whether themobile communication device has re-entered a travel state (e.g., after atemporary stop) or has entered a non-transitory state (e.g., at home orat the office). Accordingly, at decision block 724, a test is conductedto determine whether a minimum movement has been detected based on theset of inputs. If minimum movement has not been detected, the mobilecommunication device 104 is determined to be no longer in motion.Accordingly, the transit state is changed to “non-transitory” at block702 (FIG. 7A). Alternatively, if a minimum movement has been detectedbased on the set of inputs, the mobile communication device 104 isdetermined to be in transit again and the routine 700 proceed to block712 (FIG. 7B) in which the transit state is changed to city/urbantransit state. In both decision alternatives, the mobile communicationdevice 104 transmits updated context information to the communicationmanagement component 102 indicative of the change in transit state.

With reference now to FIG. 7D, if at decision block 716 (FIG. 7B), thecriteria indicative of city/urban transit state were not satisfied, themobile communication device context processing component 304 determinesthat the mobile communication device is a highway transit state,indicative of highway travel. Accordingly, at block 726, the transitstate is changed to a “highway” traveled state and the mobilecommunication device 104 transmits updated context information to thecommunication management component 102 indicative of the change intransit state. At block 728, the mobile communication device contextprocessing component 304 enters an observation window in which acollection interval may be set to a longer time period because of theexpectation for a lower variance between the sets of inputs at eachcollection interval. When the mobile communication device 104 is ahighway transit state, it can transition to a terminus state (e.g.,indicative of a completion of travel), revert back to a city/urbantransit state or remain in a highway transit state. Additionally, in anoptional embodiment, the mobile communication device context processingcomponent 304 can determine that the mobile communication device 104 isa flight state indicative of airplane travel. Accordingly, as will beillustrated in FIG. 7D, the mobile communication device contextprocessing component 304 can also reach an “in-flight” transit statefrom the highway traveled state. In all the decision alternativesinvolving a change in transition state, the mobile communication device104 transmits updated context information to the communicationmanagement component 102 indicative of the change in transit state.

At decision block 730, a test is conducted to again determine whethercriteria indicative of city/urban transit state has been satisfied. Ifthe city criteria indicative of city/urban transit state has beensatisfied, the mobile communication device context processing component304 determines that the mobile communication device 104 should revertback to a city/urban travel state and the routine 700 returns to block712 (FIG. 7B). Alternatively, if the criteria indicative of city/urbantransit state has not been satisfied, the mobile communication devicecontext processing component 304 determines that the mobilecommunication device 104 should either remain in the highway transitstate, move to a journey terminus state, or move to an in-flight state.Accordingly, at decision block 732, a test is conducted to determinewhether a minimum movement has been detected based on the set of inputs.If the minimum movement has not been detected based on the set ofinputs, the mobile communication device 104 is determined to be nolonger in motion and the routine 700 proceeds to block 720 (FIG. 7C).

If, however, at decision block 732, the minimum movement has beendetected based on the set of inputs, at decision block 734, a test isthen conducted to determine whether criteria indicative of an in-flighttransit state has been satisfied. In an illustrative embodiment,criteria indicative of an in-flight transit state can correspond toconsideration of variance thresholds for velocity, distance traveled andbearing that are indicative of patterns of air travel. The criteria mayalso include consideration of information from altimeters or the like.The thresholds may be determined by observed driving behavior, set by anadministrator or set by a particular user. If the criteria indicative ofan in-flight transit state has not been satisfied, the mobilecommunication device context processing component 304 determines thatthe mobile communication device should remain in a highway transit stateand the routine 700 returns to block 726.

With reference now to FIG. 7E, if the criteria indicative of anin-flight transit state has been satisfied, the mobile communicationdevice context processing component 304 determines that the mobilecommunication device is in-flight. Accordingly, at block 736, thetransit state is changed to an “in-flight” transit state. At block 738,the mobile communication device context processing component 304 entersan observation window for collecting the various inputs over a period oftime, which may be a longer time period. At decision block 730, a testis conducted to determine whether is conducted to determine whether oneor more in-flight distance variances have been exceeded. If the criteriaindicative of an in-flight transit state has not been satisfied, themobile communication device context processing component 304 determinesthat the mobile communication device 104 should revert back to a highwaytravel state and the routine 700 returns to block 726 (FIG. 7D).Alternatively, if the criteria indicative of an in-flight transit statehas been satisfied, the mobile communication device context processingcomponent 304 determines that the mobile communication device 104 shouldeither remain in the in-flight distance transit state or move to ajourney terminus state. Accordingly, at decision block 740, a test isconducted to determine whether a minimum movement has been detectedbased on the set of inputs. If the minimum movement has not beendetected based on the set of inputs, the mobile communication device 104is determined to be no longer in motion and the routine 700 proceeds toblock 720 (FIG. 7C). Alternatively, if minimum movement has beendetected based on the set of inputs, the routine 700 remains in anin-flight transit state and the routine 700 returns to block 736. In allthe decision alternatives involving a change in transition state, themobile communication device 104 transmits updated context information tothe communication management component 102 indicative of the change intransit state.

With reference now to FIG. 8, a routine 800 implemented by the mobilecommunication device context processing component 304 for determiningmobile communication device geospatial context information will bedescribed. In an illustrative embodiment, geospatial information may bedefined for a geographic region. The geospatial information can includea centroid, which corresponds to an approximation of the geospatialregion's central position. The centroid can be defined in terms of alongitude and latitude, x and y coordinates in a grid-type layout orother position coordinates. The geospatial information can also includea minimum radius distance that corresponds to a minimum radius that iswithin all boundaries of the geospatial region. The geospatialinformation can further include a maximum radius that corresponds to amaximum radius that is beyond all boundaries of the geospatial region.One skilled in the relevant art will appreciate that the contours ofboundaries of a geospatial region can be defined in terms of a radiusdistance plus bearing from the centroid.

With reference to FIG. 8, at block 802, the mobile communication devicecontext processing component 304 obtains the geospatial regiondefinitions from the mobile communication device context data store 308.The geospatial region definitions may be stored and maintained in avariety of formats and storage media. Additionally, the geospatialregion definitions may be prioritized in terms of order of processing bythe mobile communication device 104. At block 804, the mobilecommunication device environment interface 306 begins a collectionwindow in which a geospatial zone definition is evaluated to determinewhether the mobile communication device 104 is within the zone. Asdescribed above with regard to transit state context assessmentalgorithms, the observation window can be configured such that themobile communication device 104 collects a fixed number of sets asdefined by an information collection interval over a time period. Eachtime a set of inputs is collected a counter is decremented and theprocess continues until the targeted number of sets on inputs have beencollected (e.g., the counter is decremented to a value of “0”).Additionally, if the mobile communication device environment interface306 is currently not receiving inputs, or otherwise not acceptinginputs, the mobile communication device 104 may enter a lower powerconsumption mode in which one or more components of the mobilecommunication device 104 become inactive or enter in a low powerconsumption mode of operation. In turn, the mobile communication device104 then powers up, or wakes up, at the next information collectioninterval. The specific information collection interval implemented bythe mobile communication device context processing component 304 may bedependent on the granularity of the sensor information, the amount ofinput information that should be collected for a given transit state,and/or the likelihood of a potential change in transit state. Forexample, a longer collection interval can be set for transit states inwhich variations in the set of inputs is not expected to furtherconserve mobile communication device power.

At block 806, the mobile communication device context processingcomponent 304 obtains mobile communication location information. In anillustrative embodiment, the mobile communication device environmentinterface 306 can obtain various sensor information indicative of alocation or relative location of the mobile communication device. Forexample, the mobile communication device environment interface 306 canobtain GPS information from an attached GPS component or via wirelesscommunication from another GPS component. In another example, the mobilecommunication device environment interface 306 can interface with avehicle's navigation system to obtain location information. In stillanother example, the mobile communication device environment interface306 can interface with wireless communication equipment, such ascellular base stations, wireless network nodes (e.g., WIFI™ and WIMAX™network nodes), and obtain location information. Additionally, thesensor information can include accelerometers and compass informationthat facilitates a bearing or direction of the mobile communicationdevice.

In an additional embodiment, and as illustrated in FIG. 9, the mobilecommunication device environment interface 306 can associate locationmeta data with known signals from wireless transmitters such that adetection of a signal can provide an indication to the mobilecommunication device environment interface 306 of the relative locationof a mobile communication device 104. As explained above with regard toFIG. 7, as a mobile communication device 104 travels, signals fromspecific transmitters are detected when the mobile communication deviceis within range of the transmitter and no longer detected when themobile communication device is beyond the range of the transmitter. Inembodiments in which the mobile device detects signals from the samewireless transmitters, the mobile communication device environmentinterface 306 can associate location meta data obtained from anotherlocation source (such as a GPS component) to the information indicativeof the wireless transmitter, such as a WIFI™ SSID. Accordingly, inconjunction with the known range of the wireless transmitter, the mobilecommunication device environment interface 306 can estimate range,associate the location meta data as the approximate location of themobile communication device 104 for purposes of evaluating contextaccording geospatial zones.

For purposes of power consumption, the mobile communication deviceenvironment interface 306 can monitor various location sensors/inputs.The mobile communication device environment interface 306 can prioritizeor rank the location information sources based on various factors,including degree of confidence in the accuracy of the locationinformation, power consumption associated with collecting the locationdata, financial or service contract issues, and the like. For example,assume that a mobile communication device environment interface 306 haspreviously stored location information for a known WIFI™ wireless nodein Meta data in the manner described above. Although locationinformation may also be available for an attached GPS component,operation of the GPS component consumes much more device power.Accordingly, the mobile communication device environment interface 306could choose to receive/use location information from a source with theleast power consumption metrics.

With reference again to FIG. 8, at block 808, the mobile communicationdevice context processing component 304 calculates the distance andbearing of the current location of the mobile device to the centroid ofgeospatial zone. At decision block 810, a test is conducted to determinewhether the distance to the centroid is outside of the maximum radiusdefined for the geospatial zone. If so, at block 812, the mobiledevice's current context is outside the geospatial zone. The routine 800then proceeds to block 818, which will be described below.

If at decision block 810, the distance to the centroid is not outsidethe maximum radius, the mobile communication device context processingcomponent 304 will then determine whether the mobile communicationdevice is clearly within the geospatial zone or on the fringe ofboundary of the geospatial zone. At decision block 814, a test isconducted to determine whether the distance is less than the minimumradius defined for the geospatial zone. If so, at block 816, the mobiledevice's current context is inside the geospatial zone. The routine 800then proceeds to block 818.

At block 818, the mobile communication device 104 must transmit updatedcontext information if a context state has changed. Accordingly, if themobile communication device has not changed from outside the geospatialzone (block 812) or within the geospatial zone (block 816), no updatewill be provided. At block 820, the interval for collection of locationinformation and the evaluation of the proximity to the geospatial zonewill be decreased (or verified to be at a lower level). In either thecase of clearly outside the geospatial zone or clearly within thegeospatial zone, the likelihood of a sudden change in context decreases.For example, for a geospatial zone corresponding to an entire city, thefrequency in which the mobile device would detect a change correspondingto being detected outside the citywide geospatial zone would likely below. Accordingly, the collection interval could be adjusted in an effortto mitigate power drain associated with the collection and processing ofthe sensor information. The routine 800 then returns to block 804 forcontinued collection and processing of the information at the nextcollection interval.

Turning again to decision block 814, if the distance is not less thanthe minimum radius defined for the geospatial zone, the mobilecommunication device 104 is likely just within the boundary of thegeospatial zone or just outside the boundary of the geospatial zone.Accordingly, the mobile communication device context processingcomponent 304 can then determine with the mobile communication device104 falls within or just without. If the determined context is a changefrom a previous context, at block 822, the updated context informationis transmitted to the communication management component 102. At block824, the collection interval is increased (or verified to be at a higherlevel). In the case of neither clearly outside the geospatial zone orclearly within the geospatial zone, the likelihood of a sudden change incontext increases. Because of the potential for more likely changes incontext, the interval for collection is increased. The routine 800 thenreturns to block 804 for continued collection and processing of theinformation at the next collection interval.

B. Communications Management Component Operation

With reference now to FIG. 9, a routine 900 implemented by thecommunication processing component 204 to manage communicationsassociated with a mobile communication device 104 will be described. Atblock 902, the mobile communication device interface component 202receives mobile communication device context information from the mobilecommunication device 104. The mobile communication device contextinformation corresponds to processed inputs and is indicative of themobile communication device context. The context information may requireadditional processing by the communication management system 102. Aspreviously discussed, the mobile device communication component 202 mayutilize any number of communication channels to receive the contextinformation from the mobile communication device 104. Additionally, inthe event that the context information corresponds to updated contextinformation, especially if the mobile communication device is presentlyin an established communication channel, the mobile device communicationcomponent 202 may utilize alternative communication channels.

At block 904, the communication processing component 204 obtains mobilecommunication device profile information from the mobile communicationdevice profile store 210. The mobile communication profile data store210 can correspond to a database that identifies different mobilecommunication device profiles according to different mobilecommunication device context. For example, a mobile communication devicemay have a profile for each defined geospatial region and transit state.In this illustrative embodiment, the profile defines the availabilityfor communication channels for all incoming communication channelrequests. In an alternative embodiment, the mobile communication deviceprofile data store may maintain additional or supplemental profiles thatdefine availability for various mobile communication device contextsaccording to particular or identifiable users or groups of users. Inthis embodiment, the profile information can correspond to a routingtable that identifies availability according to context information withan identifiable user.

At block 906, the communication processing component 204 determines thecommunication channel availability according to the profile informationobtained at block 904. The availability information may be determinedupon receipt of the context information and/or may be updated uponreceipt of updated context information. Additionally, if a communicationchannel is not already established, the availability is determined priorto receiving a request for establishing a communication channel fromeither the mobile communication device 104 or a third partycommunication device 112. Still further, the communication managementcomponent 102 can also receive additional information from additionalthird party information sources for processing the profile to determineavailability. For example, the communication management system caninterface with network resources, such as calendaring applications orinterfaces, to receive user calendaring information for an identifiedperiod of time. In this example, the calendaring information may beapplied to a profile indicating communication channel availability basedon categories of appointments (e.g., unavailability for a communicationchannel based on meetings with a “High Priority” label). Additionally,the calendaring information may be utilized by the communicationmanagement system in the selection of communication mitigation options.

At block 908, the mobile service provider communication component 208obtains a notification of a request to establish a communicationchannel. The notification can include a request to provide authorizationfor establishing the requested communication channel. Alternatively, thenotification can include an indication that the communication channelwill be initiated by default unless the communication management system102 provides an indication that the communication channel should not beestablished. Additionally, the request to initiate the communication caninclude additional information regarding the identity or properties ofthe other party to the requested communication channel and that can beutilized to determine establish appointments for the user of the mobiledevice.

Returning to FIG. 9, at decision block 910, the communication processingcomponent 204 performs a test to determine whether the mobilecommunication device is available. In an illustrative embodiment, if thecommunication processing component 204 has utilized a profile that isapplicable to all users, the device availability may be quicklydetermined based on the prior processing. If, however, the mobilecommunication device profiles specifies availability based on theidentity of some third parties, the communication processing component204 looks up the specific availability of the user or groups of users.

To facilitate the processing of availability information according to anidentified user or groups of users, the communication processingcomponent 204 can utilize a fast lookup routing table that sortsavailability by the user's identity, such as phone number or IP address.In this embodiment, the data is sorted by number. As the communicationprocessing component 204 selects a first identifier in the identity,such as the first digit of the phone number, any entries in the tablenot having the matching numbers collapse. This process would continuefor each additional digit that is provided. One skilled in the relevantart will appreciate that individual users may be represented by fullidentities. Additionally, the routing table may also limit the number ofidentifiers (e.g., digits) as necessary to distinguish one user fromanother. For example, if the routing table has four users that have amatching area code and that have different third digits in their phonenumbers, the routine table may limit entries to the area code and thefirst three digits and need not enter the entire area code. Likewise,for groups of users (such as an office), the entries for the entiregroup may be limited to the identifying information from theorganization (such as the first set of digits from an IP address).

With continuing reference to FIG. 9, if the mobile communication device104 has been determined to be available, at block 912, the mobileservice provider communication component 208 transmits an authorizationto the mobile switching center 108. In the event that the routine 900 isbeing implemented for an existing communication channel, block 912, maybe omitted. The routine 900 returns to block 902.

Alternatively, if it has been determined that mobile communicationdevice 104 is not available, at block 914, the mobile service providercommunication component 208 transmits a rejection or termination messageto the mobile switching center 108. In an illustrative embodiment, therejection notice may have an immediate effect that prevents theestablishment of a communication channel. In another embodiment, thetermination notice may include a time to allow for a time period ofcontinued communication prior to termination. The communicationprocessing component 204 may select the time period according to thecontext information and the immediacy of the determined need fortermination. At block 916, the communication processing component 206processes the communication mitigation and the routine 900 returns toblock 902.

C. Communication Mitigation

In an illustrative embodiment, the communication mitigation for arejected or terminated communication channel can be specified in amobile communication device profile. As discussed above, the profile maybe described with regard to all users, groups of users and/or specificusers. In an illustrative embodiment, the communication mitigations caninclude immediate alternative communication channels/methods, such as aredirection to a voicemail system, a text to speech message processingsystem, the launching of an SMS service or email service, a redirectionto an identified backup caller (such as an operator or an assistant),and the like.

In another embodiment, the communication mitigation corresponds todelayed mitigation techniques that reestablish the requested or existingcommunication channel upon a determined availability. For example, theuser of the mobile device 104 or the third party communication device112 can request a callback or new communication channel upon a change ofmobile device context that results in the availability of the mobilecommunication device. The request can include a time component or otherinformation for specifying the expiration of the request or availabilityfor the requested callback. Additionally, the request can includeadditional information such as calendaring information for schedulingthe requested communication channel. Additionally, the calendaringinformation may be utilized to select which communication mitigationtechnique may be available.

In still a further embodiment, the communication mitigation techniquescan include the specification of immediate actions to be taken by thecommunication management system 102. In one example, a user of themobile communication device 102 can request an override of thedetermined unavailability of the mobile device. In another example, athird party associated with the communication device 112 can request apage channel to the user of the mobile device 104 to request anoverride. In a further example, a third party associated with thecommunication device 112 can request an emergency breakthrough toestablish the requested communication channel with the mobilecommunication device. In still a further example, either the userassociated with the mobile communication device 104 or the third partyuser associated with the communication device 112 can request fromseveral predefined messages to be played to the other users (such as apredetermined message requesting a driver to pull over to be able totake a call). In still a further embodiment, the communicationprocessing component 204 may initiate a timer or counter that specifiesa time limit for the user of the mobile device 104 to change theenvironment prior to the termination of an established communicationchannel or to allow for the initiation of the established communicationchannel.

In yet another embodiment of communication channel mitigationtechniques, the communication processing component 204 can implementadditional notifications to the parties requesting the communicationchannel or involved in an existing communication channel. Thenotification can include a specification of the available alternativemitigation options (described above), an explanation of why thecommunication channel was not authorized or is to be terminated and/ordetails regarding the timing for the termination of an existingcommunication channel. For example, when the communication managementsystem 102 routes an incoming call to voicemail as the result ofunavailability (e.g., the callee's mobile device is in an “intransit/city” context), an outgoing message may be played to the thirdparty communication device 112. Different messages (which may but neednot be prerecorded by the callee) may be played or generated dependingupon whether the context is “in transit/city,” “in-transit/highway,” “inmeeting,” “in geospatial zone,” “on the phone,” etc. Further, thecommunication management system 102 may output an auto-generated audiblemessage to the caller with information about the expected or estimatedfuture availability of the mobile communication device user. Forinstance, if imported calendar information indicates that the mobilecommunication device user is in a meeting, the mitigation component 206may output an audible message indicating (1) the scheduled end time of,or number of minutes remaining in, the meeting, and (2) the amount offree time until the next meeting. As another example, if the mobilecommunication device user is in a geospatial zone, the auto-generatedmessage may indicate an estimated amount of time until the mobilecommunication device is predicted to exit the geospatial zone. Themobile communication device 104 may generate such estimatesautomatically while in a geospatial zone as part of the contextassessment algorithm, and/or may periodically communicate such estimates(or significant changes thereto) to the communication management system102.

D. Provisioning of Mobile Communication Device Profiles

With reference now to FIG. 10, an illustrative screen display 1000indicative of a user interface for provisioning mobile communicationdevice profiles will be described. In an illustrative embodiment, thescreen display 1000 may be generated by the mobile communication device104 or a user at a computing device 116. The provisioning may correspondto administrator level policies set forth by enterprises, serviceproviders, or authorities. Additionally, the provisioning may correspondto policies set forth by additional identified users, such as parents.One skilled in the relevant art will appreciate that any number ofinterfaces may be generated. Additionally, various interfaces may beconfigured to correspond to the display capabilities and/or requirementsof the device generating the display. Additionally, various interfacesmay be presented according to the defined context.

With reference to FIG. 10, the screen display 1000 can include a firstsection 1002 for specifying a profile for particular type of contextinformation. As illustrated in FIG. 10, the section 1002 specifies thatavailability information is being defined for one or more geospatialzones. The section 1002 may correspond to a number of available contextinformation categories, such as a pick list or a drop down box. As alsoillustrated in FIG. 10, the screen display can include a map overlaysection 1004 for provisioning the boundaries of the geospatial zone. Theoverlay section can correspond to map information published by thecommunication management system 102 or additional third parties. Forexample, the overlay section 1004 may be an existing street map thatincludes icons indicative of well known or specified establishments. Inan illustrative embodiment, the geospatial zones may default to aselection of communication unavailability within the geospatial zone.Alternatively, a user may be able to specify the availability for thegeospatial region based on context information or specific users orgroups of users.

The screen interface 1000 can further include any number of graphicindicators of geospatial zones 1006, 1008 that will define theboundaries of the geospatial zones. In an illustrative embodiment, thegraphic indicators may be generated via various drawing tools providedon the interface 1000. In another embodiment, the graphic indicators maybe generated by the indication of the coordinates of endpoints andintersections of the boundaries. In still a further embodiment, theinterface 1000 may be provisioned with predefined geospatial boundariesthat have been provided by the communication management system 102and/or published by other users.

In another embodiment, the geospatial boundaries can be generated by theentry of location coordinates by the user via a mobile device 104. Inthis embodiment, a user can utilize location information, such as GPSinformation, to indicate the coordinates of geospatial boundaries whenthe mobile device is at the coordinates. For example, the user canselect a control or provide data via the mobile device to indicate thelocation of the boundaries.

With continued reference to FIG. 10, as previously described, theprofile information may also be specified for specific users or groupsof users. In accordance with an alternative embodiment, the screeninterface can include a representation of users or individuals as a setof icons 1010 that can be manipulated to selection the application of ageospatial zone and selected availability. For example, a user canmanipulate the icons 1010 via a drag and drop technique to apply ageospatial boundary and associated availability by dropping the icon onthe selected geospatial zone or vice versa. The screen interface 1000may also include a section 1012 in which a user can specify a type ofcommunication mitigation technique to be applied in the event ofunavailability. As illustrated in FIG. 10, a communication forwardmitigation technique has been specified.

FIG. 11 is a block diagram illustrative of a screen display 1100 of auser interface for obtaining mobile communication device profileinformation for managing mobile communication device availability basedon mobile communication device context information. The screen display1100 facilitates the specification and management of profiles forindividuals or groups of individuals. As illustrated in FIG. 11, thescreen display 1100 corresponds to a display of geometric shapes (e.g.,circles) that correspond to determined availability based contextinformation. Display objects corresponding to identified individuals canbe placed in the geometric shapes to associate the identified individualwith the determined availability. Information identified individuals maycorrespond to information obtained from a network resource, such as acontact list. The association is stored in the mobile device profiles.Additionally, summaries of the associations can be displayed in thescreen display 1100.

E. Additional Embodiments

In accordance with still another illustrative embodiment, thecommunications management component 102 may utilize learned behaviors orpredictive behaviors to provision the mobile communication deviceprofiles and/or to determine the availability of the mobilecommunication device 104. In accordance with this embodiment,communications management component 102 may track various behaviors ormobile communication device usage in the mobile communications deviceprofile data store 210. For example, the communications managementcomponent 102 may track the length of audio conversations betweenspecific users or groups of users. In another example, thecommunications management component 102 may also track the timing ofrequests for communication channels on a daily, weekly, or monthlybasis. In still a further example, the communication management system102 may track previous determined unavailability to generate a model ofavailability for users based on time of day or based on events. Withcontinued reference to the example, the communications managementcomponent 102 may associate events on a calendar (such as specificreoccurring meetings) with mobile communication device contextinformation that generates a determination of unavailability (such astraveling within a defined geospatial zone). Accordingly, a profile maybe provisioned such that the communication processing component 204 mayutilize user calendaring function inputs to determine unavailability inadvance. Additionally, users may be asked to identify specific ornotable events that facilitate the learned behavior approach.

In a related embodiment, the communication processing component 204 mayalso utilize learned behavior to adjust a determination of availability.For example, assume that an identified user typically has audiocommunications with another user for 20 minutes or greater on a frequentbasis. Also assume that at current time, the mobile device is availablefor audio communication channels. However, the current bearing andvelocity will likely place the mobile communication device 104 within ageospatial zone defining unavailability in the next 10 minutes oftravel.

In this embodiment, the communication processing component 204 caninclude learned behaviors to determine whether it would have to likelyterminate the communications channel. If so, the communicationprocessing component 204 may adjust the determination of availability inthe event that the anticipated time of the communication channel cannotbe completed. Thus, in the above example, the communication processingcomponent 204 can determine that the user will likely be entering ageospatial zone based on a current velocity and bearing. Additionally,because of learned behaviors or historical knowledge, the communicationprocessing component 204 can anticipate that the length of the audiocommunication and will require the communication channel to beterminated when the mobile communications device enters the geospatialzone. Accordingly, the communication processing component 204 maychoose, based on its own configurations or a configuration specified bythe user, to not authorize the communications channel and offer aselection of communication mitigation approaches.

In another example, the communication processing component 204 canmonitor a user's repeated selection of communication mitigationtechniques as part of an interactive voice response as a function of anidentified user or a specific mobile device context. Accordingly, thecommunication processing component 204 may update applicable mobilecommunication device profiles in view of a number of predeterminedselections of communication mitigation techniques.

In still another example, the communication processing component 204 canmonitor a determination of repeated unavailability according to a timeof day or other identified event. Accordingly, the communicationprocessing component 204 may update applicable mobile communicationdevice profiles in view of a number of determinations such that aprofile can specify automatically specify unavailability as a functionof the determined time of day or event. For example, if a mobilecommunication device 104 is determined to be unavailable every for twoconsecutive weeks at the same time, the communication processingcomponent 204 may update a profile to make the unavailability determinea function of time.

In yet a further example, communication processing component 204 canmonitor a number of communication requests from a previouslyunidentified third party communication device 112 or for a communicationdevice that is not associated with a mobile communication deviceprofile. After a number of repeated communication requests, thecommunication processing component 204 may automatically create a mobilecommunication device profile or prompt a user for the creation of themobile communication device profile for such third party communicationdevice. The communication processing component 204 can automaticallypopulate some or all of the aspects of the profile based on thepreviously monitored activity. Additionally, it can import a template ofprofile information set by the user, an administrator, or a serviceprovider.

In accordance with another embodiment, the context information and/oravailability generated by the mobile communication device 104 or thecommunications management component 102 may be published to additionalinformation sources/repositories, such as network resources. In oneexample, the mobile device 104 or communications management component102 may publish a set of the geospatial zones that a user has created.The published geospatial zones may be used by other system users toprovision mobile communication device profiles. The published geospatialzones may be utilized to describe/publish the context information thatwill be used by the communications management component 102 to determineavailability.

In another embodiment, the mobile communication device contextinformation may be published to other information sources/repositoriesto publish the current or past mobile device contexts. In one example,the mobile device context information can be linked with a personal Webpage of a user, such that context information (e.g., in transit) ispublished on the Web page. In another example, the mobile device contextinformation can be linked with a calendaring function to determinewhether the user is on schedule. If for example a user remains in acity/urban transit state due to traffic conditions, subsequentappointments may need to be rescheduled or cancelled. Accordingly, acontrol algorithm may automatically cancel meetings or provideappropriate notifications. In still another embodiment, thedetermination of a proximity to a geospatial zone or entry into ageospatial zone may be published to a third party source to initiateadditional actions (e.g., a communication to security personnel).

In still another embodiment, the mobile communication deviceavailability information may also be published to other informationsources/repositories. Similar to the published context information, themobile device availability information can be linked with a personal Webpage of a user, such that availability information (e.g., in transit) ispublished on the Web page. In another example, the mobile deviceavailability information can be linked with a calendaring function andpublished to allow for scheduling of current or future events. In stilla further example, the published availability information (historicaland current) may be used to generate and published a model ofavailability. In such an embodiment, other users may be presented withopportunities for predictive availability. Still further, theavailability information may be filtered according to the authorizationto different users or classes of users.

Bypassing Mitigation Services

As previously described, in one embodiment, the communication processingcomponent 204 manages a subscriber terminal state with regard to whethercall mitigation services should be applied to a communication request tothe mobile device 104. In scenarios involving the communication betweena mobile device 104 and a PSAP center 114, the communication processingcomponent 204 can utilized mobile device context state to determinewhether communication mitigation techniques should be bypassed.

With reference now to an illustrative interaction if FIGS. 12A-12C, asillustrated in FIG. 12A (and previously described), during the operationof the mobile communication device 104, or during an initialization ofthe mobile communication device, the mobile communication deviceinterface component 306 obtains a set of inputs corresponding to themobile communication device environment. The set of inputs are processedby the mobile communication device context processing component 304 togenerate mobile communication device context information. Thecommunication management system communication component 302 thentransmits the mobile communication device context information to thecommunication management system 102 as appropriate. Specifically, toreduce power consumption and/or bandwidth consumption, the communicationmanagement system communication component 302 may limit the transmissionof mobile communication device context information for theinitialization of a mobile communication device context, a detection ofa change in mobile communication device context and/or for there-establishment of a mobile communication device context.

Upon receipt of the context information, the mobile device communicationcomponent 202 transmits the context information to the communicationprocessing component 204 for processing. The communication processingcomponent 204 obtains one or more corresponding, or applicable, mobilecommunication device profiles from the mobile communication deviceprofile data store 210. The communication processing component 204 thendetermines the availability of the mobile communication device toestablish a communication channel (either receipt of a request or theinitiation of a request) based on the processing.

Thereafter, in the illustrative example of FIG. 12A, the mobile device104 initiates a request to establish a communication channel with acommunication device 112, such as a PSAP center 114. In the illustrativeembodiment, the initiation of a request to establish a communicationchannel with the PSAP center 114 can be designated as a communication inwhich communication mitigation techniques may be bypassed. In such asituation, the mobile device 104 can be referred to as entering a bypassstate. In one example, the mobile switching center 108 or communicationmanagement system 102 may be able to classify the call as requiring abypass state based on the contact information (e.g. phone number orother call identification information) of the communication device 112.In another example, the mobile device 104 may independently transmit anotification that requests that the phone enter into a bypass state orinformation that allows the communication management system 102 todetermine that the mobile device 104 should be designated in a bypassstate. In another example, the receiving communication device 112 canprovide an independent notification that the requesting mobile device104 be designated as entering a bypass state. Accordingly, thecommunication management system 102 can determine that the mobile device104 should be designated in a bypass state. By way of illustrativeexample, in an emergency situation in which safety personnel such aspolice, ambulance, or firefighting personnel have been contacted, one ormore mobile devices 104 may be designated for entering into a bypassstate.

With reference to FIG. 12B, upon receipt of the notifications orinformation regarding the bypass state, the communication managementsystem 102 updates the determination of the context informationassociated with the mobile device 104. In an additional embodiment, thecommunication management system 102 may also update the contextinformation for other devices that may be associated with a designatedmobile device 104. For example, in the case of an emergency, such as abuilding lockdown, the communication management system 102 may designateall employees having company affiliated mobile devices to be in a bypassstate. In an illustrative embodiment, the communication managementsystem 102 can maintain logs of the information that can be used forbilling purposes (e.g., billing for emergency calls) or other auditingpurposes. Additionally, the communication management system 102 canimplement additional notification routines that information other usersand/or identified devices of the bypass state. The notification routinesmay be stored or configured for the subscriber. With regard to themobile device 104 requesting the communication channel, the mobileswitching center 108 establishes the communication channel between thecommunication device, such as PSAP center 114 and the mobile device.

Turning now to FIG. 12C, if the communication channel between the PSAPcenter 114 and mobile device 104 is terminated prematurely, the PSAPcenter 114 will attempt to initiate a call to the mobile device 104 ofthe subscriber that initiated the call. The telephony network willcomplete the call back towards the mobile switching center 108 that isserving the mobile device 104 in the normal fashion. At each stage inthe call completion as the call traverses the mobile switching center108 elements in the network, the mobile switching center 108 may beinstructed to run advanced call mitigation services (as describedabove). If this is the case, then prior to invoking any query to ascreening service, the mobile switching center 108 will invoke a querytoward the communication management system 102 for the mobile device104. In the case of the illustrative dropped PSAP center communicationchannel, the communication management system 102 will notify the mobileswitching center 108 that the mobile device 104 is currently in a bypassstate. The mobile switching center 108 will then bypass any advancedsubscriber services (e.g., communication mitigation services).Additionally, the communication management system 102 can classify thecall (e.g., an emergency call or a classified call) and associatepriority routing/designation. The communication channel can bereestablished.

The bypass state designation for a mobile device 104 can persist untilit is cleared either by the network, or by the mobile device 104. Forexample, the bypass state can be cleared based on subsequent activityinitiated by the mobile device 104, such as transmitting an explicitrequest to terminate the bypass request, initiating a communicationrequest to a device not associated with the bypass state (e.g., a callwith nonemergency personnel), and the like. The bypass state designatedfor a mobile device 104 can also be cleared by the network a prescribedamount of time after the state is initiated, i.e. the state times out inthe communication management system 102.

With reference now to FIG. 13, a flow diagram illustrative of a callmitigation bypassing processing routine 1300 implemented by acommunication management component 102 will be described. At block 1302,the communication management component 102 obtains a call mitigationservice bypass request. As described above, in one embodiment, themobile device 104, mobile switching center 108, or other component mayspecifically transmit the request to the communication management system102. Alternatively, the mobile device 104, mobile switching center 108,or other components may transmit information (independently orcumulatively) that facilitates the determination of mobile devicecontext. At block 1304, the communication management system 102designates the mobile device 103 in a bypass state. In one embodiment,in the event that the communication management system 102 supportsmultiple call mitigation or call bypass services, the designation of abypass state may be with regard to specific services, types/classes ofservices or all services.

At decision block 1306, the communication management system 102 a testis conducted to determine whether the communication management system102 has obtained a bypass state query from the mobile switch center 108.As previously described, the request may originate from a device, e.g.,the PSAP center 114, previously associated with the bypass state or anindependent communication device 112. Still further, the request mayoriginate from the mobile device 104 associated with the bypass state.If the communication management system 102 obtains the bypass statequery (e.g. a communication channel request), the communicationmanagement system 102 provides an indication to the mobile device 104 isassociated with a bypass state at block 1308 as applicable. In oneexample, if the communication request corresponds to a component alsoassociated with the bypass state designation, the communicationmanagement system 102 can identify the parties accordingly andcommunication mitigation procedures may be bypassed. In another example,if the communication request corresponds to a component not otherwiseassociated with the bypass state, the communication management system102 can identify the parties accordingly and the communicationmitigation procedures may still apply.

At block 1310, the communication management system 102 processes thebypass state information. In an illustrative embodiment, thecommunication management system 102 can determine whether it shouldupdate the bypass state information previously associated with thedevice. For example, if the mobile device 104 has initiated a subsequentcommunication channel request to a component not otherwise associatedwith the previous bypass state, the communication management system 102can determine that the mobile device 104 should not longer be designatedas in the bypass state. In another example, if additional components areassociated with the bypass state, the communication management system102 may escalate the designation of the bypass state, adjust thepriority of routing, and the like.

With reference to decision block 1304, if the communication managementsystem 102 has not received a query from the mobile switching center 108(decision block 1306) or after processing the bypass state information(block 1310), the communication management system 102 determines whetherthe bypass state information has been updated. If the bypass informationhas not been updated, the routine 1300 returns to decision block 1306.If the bypass information has been updated, the communication managementsystem 102 designates the mobile device 104 in the updated state and theroutine 1300 terminates.

Turning now to FIG. 14, a flow diagram illustrative of a call mitigationbypass initiation routine 1400 implemented by a mobile device 104 willbe described. At block 1402, the mobile device 104 obtains a designationto enter into a bypass state. In one embodiment, a mobile device mayinclude interfaces, such as buttons, soft buttons, display objects,voice prompts, etc., that can be used to obtain a designation by a userto enter into a bypass state. In another embodiment, the designation maybe inferred by the recognition of specific words, telephone numbers,addressing, and the like. In that embodiment, the mobile device 104 maybe configured specifically by a user to make such inferences. At block1404, the mobile device 104 can transmit the obtained designation.Illustratively, the designation may be transmitted to a communicationmanagement system 102 or the mobile switch center 108 as a separatetransmission or as part of a communication request.

Thereafter, assuming the mobile device 104 has been associated with abypass state, at decision block 1406, a test is conducted to determinewhether the bypass state should be updated. In one embodiment, themobile device may use the same (or different) interfaces, such asbuttons, soft buttons, display objects, voice prompts, etc., that can beused to obtain a designation by a user to enter modify the bypass state.In another embodiment, the mobile device 104 may determine an intent toupdate the bypass state by the passage of time without activity,keywords, the request to generate subsequent communication channels, andthe like. The determination of a request to modify the bypass state maybe in conjunction with another component (such as the communicationmanagement system 102) or independent from other components.

If the bypass state should not be updated, the routine 1400 returns todecision block 1406. Alternatively, if the bypass state should beupdated, the mobile device 104 transmits the designation to update thebypass state. In the same manner described above, the designation may betransmitted to a communication management system 102 or the mobileswitch center 108 as a separate transmission or as part of acommunication request. The routine 1400 terminates at block 1410.

Turning now to FIG. 15, a flow diagram illustrative of a call mitigationbypass processing routine 1500 implemented by a network node, such asthe mobile switching center 108, will be described. At block 1502, themobile switching center 108 obtains a request to transfer communicationsto a mobile device 104. At decision block 1506, a test is conducted todetermine whether the designated mobile device 104 is associated with abypass state. If the mobile device 104 is associated with a bypassstate, the mobile switching center 108 bypasses any otherwise applicableenhanced services and completes the communication channel request to thedesignated mobile device 104. In an embodiment having multiple potentialbypass states, the mobile switching center 108 may determine whether theassociated bypass state would apply to the requested communication. Theroutine 1500 returns to decision block 1506 to wait for furthercommunication requests.

If the mobile device is not in a bypass state at decision block 1506, atblock 1510, the mobile switching center 108 transfers the communicationrequest to an appropriate enhanced services component, such as a callmitigation component. The request can be process in the manner describedabove. At decision block 1512, a test is conducted to determine whetherthe bypass state should be updated. As previously described, a requestto update a bypass state may be transmitted from a mobile device 104 ordetermined by the communication management system 102. Additionally, themobile switching center 108 can also determine whether a bypass stateshould be updated based on information associated with the requestedcommunication channel (e.g., the initiation of a call by the mobiledevice 104) or other information. If the bypass state should not beupdated, the routine 1500 returns to block 1506. If the bypass stateshould be updated, the mobile switching center 108 transmits thedesignation of updating the bypass state to the communicationsmanagement system 102 and the routine 1500 terminates.

While illustrative embodiments have been disclosed and discussed, oneskilled in the relevant art will appreciate that additional oralternative embodiments may be implemented within the spirit and scopeof the present disclosure. Additionally, although many embodiments havebeen indicated as illustrative, one skilled in the relevant art willappreciate that the illustrative embodiments do not need to be combinedor implemented together. As such, some illustrative embodiments do notneed to be utilized or implemented in accordance with the scope ofvariations to the present disclosure.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagramsdescribed herein and/or depicted in the attached figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or steps in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those skilled in the art. It willfurther be appreciated that the data and/or components described abovemay be stored on a computer-readable medium and loaded into memory ofthe computing device using a drive mechanism associated with acomputer-readable medium storing the computer executable components,such as a CD-ROM, DVD-ROM, or network interface. Further, the componentand/or data can be included in a single device or distributed in anymanner. Accordingly, general purpose computing devices may be configuredto implement the processes, algorithms, and methodology of the presentdisclosure with the processing and/or execution of the various dataand/or components described above. Alternatively, some or all of themethods described herein may alternatively be embodied in specializedcomputer hardware. In addition, the components referred to herein may beimplemented in hardware, software, firmware or a combination thereof.

It should be emphasized that many variations and modifications may bemade to the above-described embodiments, the elements of which are to beunderstood as being among other acceptable examples. All suchmodifications and variations are intended to be included herein withinthe scope of this disclosure and protected by the following claims.

What is claimed is:
 1. A computer-implemented method, comprising:receiving a first context message identifying a first context state of amobile device, wherein the first context state is one of a plurality ofdefined potential context states, each of the plurality of definedpotential context states corresponding to a range of potential sensorinformation regarding an environment of the mobile device, and whereinan availability of the mobile device to establish communication isdefined as a function of a previously received context state of themobile device, independent of specific sensor information on which thepreviously received context state is based; independent of processingthe specific sensor information on which the first context state isbased, processing the first context state to determine that theavailability of the mobile device corresponds to providing enhancedcommunication services to the mobile device, wherein the enhancedcommunication services disallow at least one request for communicationincluding the mobile device; receiving a second context messageidentifying a second context state of the mobile device, wherein thesecond context state is one of the plurality of defined potentialcontext states; independent of processing the specific sensorinformation on which the second context state is based, processing thesecond context state to determine that the updated availability of themobile device corresponds to bypassing the enhanced communicationservices to the mobile device; receiving the at least one request forcommunication including the mobile device; and allowing the least onerequest for communication including the mobile device in accordance witha bypass of the enhanced communication services to the mobile device.